This document is for users who are migrating from Multi-Ad Creator 4.0.5 or earlier (back to 3.6) to the Windows version of MultiAd Creator 6. We╒ll refer to Creator 4.0.5 and earlier as Creator 4 in this document.
There are three problems in moving files from Creator 4 to the Windows platform:
1) The older Creator file format contains essential data in the resource fork of the file. Resource forks are a feature that is exclusive to the Macintosh file system, so that data would be lost if the file was simply copied to a Windows computer.
2) Creator 4 stores PICT data for some graphics. PICT is a graphics format that is proprietary to the Macintosh graphics system.
3) Font names in files created by Creator 4 and earlier are QuickDraw font names. The same font on a Windows computer doesn╒t have the QuickDraw font name, and the QuickDraw name is often different from other names of the font, so font matching would often fail.
In order to solve these problems, we created the Creator Migration Tool. Creator Migration Tool is a drag and drop utility that runs on the Macintosh and converts document files from Multi-Ad Creator 4.0.5 and earlier to files that are readable by the Windows version of MultiAd Creator 6. When a Creator file is dropped on the application╒s icon, a converted version of that file is made. The original is not deleted or replaced. When a folder is dropped on the application icon, converted versions of all of the Creator 4 files in that folder or any of its subfolders are made, each converted file being saved in the same folder as the original.
The converted files have been modified from the original to fix the three problems above:
1) All data from the resource fork has been moved to the data fork.
2) Embedded PICT graphics (including standalone picts, EPS previews, document previews, and border segments) have been converted to PC-readable formats.
3) A font name map has been added to the file mapping QuickDraw font names to platform-independent font names.
The font name map feature only works for fonts that are currently active on the machine running Creator Migration Tool. There is a way to create a font map for all of the fonts in your library that can be used by MultiAd Creator 6 when loading converted Creator 4 files that contain incomplete font maps.
To make a master font map, make sure all of the fonts that need to be mapped are active and choose Generate Font Map from the Font Map menu in Creator Migration Tool. You will be prompted to save a file named MacFontList.txt. By default, it will save this list in the MultiAd Creator Add-Ons folder of MultiAd Creator 6, if it is installed on the machine. You can save the file anywhere you like, but you should not change the default file name.
If you can╒t get all of the fonts in your library active at once (for example, if they are not all installed on the same machine), you can use the Merge Font Map command in the Font Map menu of Creator Migration Tool. This will ask you to choose a MacFontList.txt file previously generated by Generate Font Map and will merge all of the currently active fonts into it. This process can be repeated until the font map contains entries for all of the fonts in your library. You can examine the contents of this file with any text editor.
MultiAd Creator 6 automatically uses such a font map if it is named MacFontList.txt and stored in the MultiAd Creator Add-Ons folder. To make it useable from the Windows version of MultiAd Creator 6, copy it to the MultiAd Creator Add-Ons folder in the Creator folder on the Windows machine. It should be copied to every Windows machine that will be used to open Creator 4 files.
Note: The MacFontList.txt file is also used when loading CIF files.
Note: The MacFontList.txt file can also be used by MultiAd Creator 6 on the Mac OS to get more information about missing fonts when loading Creator 4 files.
It is possible to use the MacFontList.txt file to substitute a different font for a font that doesn╒t exist on the Windows platform. This requires hand-editing the file. The file is a text file delimited by returns and tabs. Each return-delimited record contains tab-delimited fields describing one font. The fields, in order, are:
QuickDraw name
Style (a number: usually 0 for Plain, 1 for Bold, 2 for Italic, or 3 for Bold Italic)
PostScript name
Full name
Family name
Style name
So, for example, to change Apple Chancery to Shelley Volante Script, you would edit the Apple Chancery entry in the MacFontMap.txt file to use the PostScript name, Full name, Family name, and Style name of Shelley Volante Script, like so:
Of course, <tab> would be just a tab character, <return> would be just a return character, and the spaces around those markers would be omitted.
Note: standard text files on Windows use a different line ending character from standard text files on the Mac OS. Creator Migration Tool saves the MacFontList.txt using a line ending convention more compatible with Windows text editors than Mac text editors. On some Mac text editors, such as SimpleText, the Windows line endings are displayed as ╥missing characters╙ (a small rectangle). Others, such as BBEdit, recognize and handle the Windows line endings for what they are. Creator 6 doesn╒t care what line ending convention is used in this file, so it should work properly whether you edit the file on a Mac or a Windows computer.
